My thoughts are AE has always leveraged its developer community as part of its community building program. Every successful app requires an eco-system made up of users, developers, and trainers and each have their own eco-system. Also, while it is possible the AE Team may eventually make this feature part of the main app, the danger is they may be digging a rabbit hole they don't want to be it. Solving for one feature may require solving for related issues/features and while possibly not an endless series of tasks, there is the issue of Opportunity Costs and whether a third party can solve for the feature reliably and for the long-term. I develop MoGraph Design Systems and a critical requirement is to analyze requirements from a Systems Thinking POV - with Text Layers, things get very wide and deep very quickly and for my use-case, a Text Layer's position, other than its Anchor Point/Baseline also forms a critical part of an overall solution. So, it won't be long before user-expectations expand to meet their needs and this is where the rabbit hole gets deeper. So, what may seem like a short term solve actually involves a deeper and longer-running commitment. This is also why you should go on a few dates before deciding to get married. 😉
... View more